Skip to content

Add explicit debounce of 5ms to fix double keypress issue#5

Open
jkquickstar wants to merge 1 commit intoEpomaker:mainfrom
jkquickstar:fix/debounce-double-keypress
Open

Add explicit debounce of 5ms to fix double keypress issue#5
jkquickstar wants to merge 1 commit intoEpomaker:mainfrom
jkquickstar:fix/debounce-double-keypress

Conversation

@jkquickstar
Copy link
Copy Markdown

Summary

  • The shipped firmware (from hangshengkeji/qmk_firmware) sets debounce to 1ms, which is far too low to filter mechanical switch contact bounce (typically 5-15ms), causing intermittent double key registrations
  • Adds an explicit "debounce": 5 to info.json to match the QMK recommended default and prevent the issue from recurring in future builds
  • Verified fix resolves double keypress on physical TIDE 75 hardware

Test plan

  • Flashed firmware with debounce set to 5ms on TIDE 75 hardware
  • Confirmed double keypress issue is resolved across all keys
  • Maintainer verification on additional TIDE 75 units

🤖 Generated with Claude Code

The shipped firmware (from hangshengkeji/qmk_firmware) sets debounce to
1ms, which is too low to filter mechanical switch contact bounce (typically
5-15ms). This causes intermittent double key registrations. Setting
debounce to 5ms (the QMK default) resolves the issue.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant